Functionality watermarking and management

ABSTRACT

A method, system and non-transitory computer-readable medium product are provided for functionality watermarking and management. In the context of a method, a method is provided that includes identifying a request to establish an association between a watermark template and a function of at least one user device and determining whether the request to establish the association between the watermark template and the function of the at least one user device is authorized. The method further includes authorizing the request to establish the association between the watermark template and the function of the at least one user device in response to a determination that the request to establish the association between the watermark template and the function of the at least one user device is authorized.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/959,899 filed on Aug. 6, 2013, entitled “FUNCTIONALITY WATERMARKINGAND MANAGEMENT,” now issued as U.S. Pat. No. 8,806,217, which is acontinuation-in-part of U.S. patent application Ser. No. 13/934,386filed Jul. 3, 2013, entitled “FUNCTIONALITY WATERMARKING ANDMANAGEMENT,” now issued as U.S. Pat. No. 8,756,426, the entiredisclosures of which are hereby incorporated by reference, for allpurposes, as if fully set forth herein.

BACKGROUND

Functionality Watermarking and Management provides determining whetheridentified requests to establish an association between watermarktemplates and functions of user devices are authorized. Additionally,Functionality Watermarking and Management provides authorizing anestablishment of an association between watermark templates andfunctions of user devices in response to determinations that respectiverequests are authorized. In some situations, requests to establish anassociation between watermark templates and functions of user devicesshould not be permitted. Conventional approaches do not address thisproblem, but rather freely allow associations to be established betweenwatermark templates and functions of user devices.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is neither intended to identify key featuresor essential features of the claimed subject matter, nor is this Summaryintended to limit the claimed subject matter's scope.

A method, apparatus and non-transitory computer-readable medium productare provided for functionality watermarking and management. In thecontext of a method, a method is provided that includes identifying arequest to establish an association between a watermark template and afunction of at least one user device and determining whether the requestto establish the association between the watermark template and thefunction of the at least one user device is authorized. The methodfurther includes authorizing the request to establish the associationbetween the watermark template and the function of the at least one userdevice in response to a determination that the request to establish theassociation between the watermark template and the function of the atleast one user device is authorized.

It is to be understood that both the foregoing general description andthe following detailed description are examples and explanatory only,and should not be considered to restrict the disclosure's scope, asdescribed and claimed. Further, features and/or variations may beprovided in addition to those set forth herein. For example, embodimentsof the disclosure may be directed to various feature combinations andsub-combinations described in the detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood withreference to the following diagrams. The drawings are not necessarily toscale. Instead, emphasis is placed upon clearly illustrating certainfeatures of the disclosure. Moreover, in the drawings, like referencenumerals designate corresponding parts throughout the several views. Inthe drawings:

FIG. 1 is a block diagram of a user device;

FIG. 2 is a block diagram of an operating environment; and,

FIG. 3 and FIG. 4 are flow charts illustrating methods for providingfunctionality watermarking and management.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar elements.While embodiments of the disclosure may be described, modifications,adaptations, and other implementations are possible. For example,substitutions, additions, or modifications may be made to the elementsillustrated in the drawings, and the methods described herein may bemodified by substituting, reordering, or adding stages to the disclosedmethods. Accordingly, the following detailed description does not limitthe disclosure. Instead, the proper scope of the disclosure is definedby the appended claims.

Functionality watermarking and management may be provided. Functions ofuser devices may include, but are not limited to, hardware functionssuch as camera functions, software functions such as voice activatedfunctions, and application functions such as containerized documentaccess and/or annotation functions. Functions of user devices may haveaccess to resources stored on the user devices and/or stored on serverscommunicatively coupled to the user devices, which may be utilizedduring the execution of the functions of the user devices. To ensure thesecurity of functions of user devices and/or resources accessible tofunctions of user devices, watermark templates may be applied to suchfunctions and/or resources.

Watermark templates may describe and/or control the use of functions ofuser devices and/or resources accessible to functions of user devices.Watermark templates may be compiled of watermark template elements,which may include, for example, descriptive data elements, namingconvention elements, and storage structure convention elements. Somewatermark template elements, such as descriptive data elements, maysecure functions of user devices and/or resources accessible tofunctions of user devices by, for instance, describing such functionsand/or resources as sensitive. Some other watermark template elements,such as naming convention elements and storage structure conventionelements, may secure functions of user devices and/or resourcesaccessible to functions of user devices by, for example, restricting theuse of such functions and/or resources to secure uses.

Applying watermark templates to functions of user devices and/orresources accessible to such functions requires that an associationbetween such watermark templates and such functions and/or suchresources be established to provide a basis for determining whichwatermark templates should be applied to which functions and/or whichresources. In other words, there must be a relationship establishedbetween watermark templates and functions of user devices and/orresources accessible to functions of user devices to facilitate anapplication of such watermark templates to such functions and/or suchresources. To prevent unauthorized associations from being establishedbetween watermark templates and functions of user devices and/orresources accessible to functions of user devices, an IT administratormay configure compliance rules that must be satisfied before anassociation may be established between watermark templates and functionsof user devices and/or resources accessible to functions of userdevices.

This process may be implemented through a method that identifies arequest to establish an association between a watermark template and afunction of at least one user device, determines whether the request toestablish the association between the watermark template and thefunction of the at least one user device is authorized, and authorizesthe request to establish the association between the watermark templateand the function of the at least one user device in response adetermination that the request to establish the association between thewatermark template and the function of the at least one user device isauthorized.

FIG. 1 is a block diagram of a user device 100. User device 100 maycomprise a processor 105 and a memory 110. For example, user device 100may comprise a personal digital assistant, a smart phone, a cellulartelephone, a desktop computer, a laptop computer, a set-top box, a musicplayer, a web pad, a tablet computer system, a game console, and/or anyother device with like capability. Depending on the configuration andtype of device, memory 110 may comprise, but is not limited to, volatile(e.g. random access memory (RAM)), non-volatile (e.g. read-only memory(ROM)), flash memory, or any combination. Memory 110 may storeexecutable programs and related data components of various applicationsand modules for execution by user device 100. Memory 110 may be coupledto processor 105 for storing configuration data and operationalparameters, such as commands that are recognized by processor 105.

Basic functionality of user device 100 may be provided by an operatingsystem 115 contained in memory 100. One or more programmed softwareapplications may be executed by utilizing the computing resources inuser device 100. Applications stored in memory 110 may be executed byprocessor 105 (e.g., a central processing unit or digital signalprocessor) under the auspices of operating system 115. For example,processor 105 may be configured to execute applications such as webbrowsing applications, email applications, instant messagingapplications, and/or other applications capable of receiving and/orproviding data.

Data provided as input to and generated as output from theapplication(s) may be stored in memory 110 and read by processor 105from memory 110 as needed during the course of application programexecution. Input data may be data stored in memory 110 by a secondaryapplication or other source, either internal or external to user device100, or possibly anticipated by the application and thus created withthe application program at the time it was generated as a softwareapplication program. Data may be received via any of a plurality ofcommunication ports 120(A)-(C) of user device 100. Communication ports120(A)-(C) may allow user device 100 to communicate with other devices,and may comprise components such as an Ethernet network adapter, amodem, and/or a wireless network connectivity interface. For example,the wireless network connectivity interface may comprise at least one ofa PCI (Peripheral Component Interconnect) card, USB (Universal SerialBus) interface, PCMCIA (Personal Computer Memory Card InternationalAssociation) card, SDIO (Secure Digital Input-Output) card, NewCard,Cardbus, a modem, a wireless radio transceiver, and/or the like.

User device 100 may also receive data as user input via an inputcomponent 125, such as a keyboard, a mouse, a pen, a stylus, a soundinput device, a touch input device, a capture device, etc. A capturedevice may be operative to record user(s) and capture spoken words,motions and/or gestures, such as with a camera and/or microphone. Thecapture device may comprise any speech and/or motion detection devicecapable of detecting the speech and/or actions of the user(s).

Data generated by applications may be stored in memory 110 by theprocessor 105 during the course of application program execution. Datamay be provided to the user during application program execution bymeans of a display 130. Consistent with embodiments of this disclosure,display 130 may comprise an integrated display screen and/or an outputport coupled to an external display screen.

Memory 110 may also comprise a platform library 140. Platform library140 may comprise a collection of functionality useful to multipleapplications, such as may be provided by an application programminginterface (API) to a software development kit (SDK). These utilities maybe accessed by applications as necessary so that each application doesnot have to contain these utilities thus allowing for memory consumptionsavings and a consistent user interface.

Memory 110 may further comprise a data store 150, within which userdevice 100 may store a plurality of user device 100 files. User device100 may, for instance, store in the data store 150 a device profile 152.Device profile 152 may comprise one or more indications of the state ofuser device 100. For instance, device profile 152 may represent deviceidentifiers unique to user device 100, user identifiers and/orcredentials associated with one or more users of user device 100,hardware features and/or components of user device 100, version andconfiguration information of various software features and applicationsinstalled on user device 100, data transmission protocols enabled onuser device 100, version and usage information of various resourcesstored on user device 100, and/or any other attributes associated withthe state of user device 100. The device profile 152 may furthercomprise data indicating a date of last virus scan of user device 100, adate of last access by an IT representative, a date of last service bythe IT representative, and/or any other data indicating maintenance andusage of user device 100. Moreover, the device profile 152 may compriseindications of the past behavior of associated users, such as accessesto one or more resource 154, charges for such accesses, and theinventory accessed from such resources 154. Furthermore, device profile152 may indicate a current location associated with user device 100and/or a home location associated with user device 100. Similarly,device profile 152 may indicate a current time associated with userdevice 100 and/or a home time associated with user device 100, such as atime associated with a home location associated with user device 100.Device profile 152 may, for example, comprise data accessible to userdevice 100 via functions of user device 100, such as GPS location data,and/or via remote services communicatively coupled to user device 100,such as current time data provided by a remote time service.

User device 100 may be operable to perform at least one function.Functions of the user device 100 may include hardware functions,software functions, and applications executed by the user device 100.Hardware functions may include functions performed by hardware built-into the user device 100, such as camera functions, microphone functions,video playback functions and/or the like. Hardware functions may furtherinclude functions performed by hardware communicatively coupled to theuser device 100, such as Google Glass functions, printer functions,scanner functions, and/or other functions performed by peripheraldevices. Software functions may include functions performed by softwarefeatures of the user device 100, such as Siri and/or similarvoice-activated functions that control the user device 100 withoutphysical input to the user device 100. Furthermore, applications mayinclude containerized applications configured for secure resource 154distribution and access, secure browser applications,enterprise-developed applications, applications wrapped with applicationwrappers, and/or other applications executable by the user device 100.

Functions of user device 100 may have access to at least one resource154. Resources 154 may be utilized by functions of the user device 100when the user device 100 performs the functions. In certain embodiments,functions of user device 100 may access existing resources 154 requiredfor execution of the functions. For instance, Google Glass functions mayrequire access to GPS resources 154 provided by a GPS sensor of the userdevice 100, which may be paired with the Google Glass functions via aBluetooth sensor, for the Google Glass functions to perform navigationfunctionality. In some embodiments, functions of user device 100 maycreate new resources 154 when executing the functions. For example, acamera function of the user device 100 may create photo and/or videoresources 154 while executing the camera function.

User device 100 may store at least one resource 154 in the data store150. Resources 154, for instance, may include any electronic data, suchas databases, applications, text files, word processor files,spreadsheet files, presentation files, graphic files, audio files,photographic files, video files, applications and application files,and/or the like. More specifically, resources 154 may include at leastone of the following file types: data files, audio files, video files,three-dimensional image files, raster image files, vector image files,page layout files, spreadsheet files, database files, executable files,CAD files, web files, plug-in files, font files, system files, settingsfiles, encoded files, compressed files, disk image files, developerfiles, backup files, and/or any other files. User device 100 may alsoaccess at least one resource 154 stored in a resource server 210 and/oranother server communicatively coupled to user device 100, as describedherein.

In certain embodiments, functions of the user device 100 may beassociated with an enterprise and/or may be personal to a user of theuser device 100. Similarly, resources 154 accessible to functions of theuser device 100 may be associated with an enterprise and/or may bepersonal to a user of the user device 100. In some embodiments, userdevices 100 may be utilized to perform both enterprise and personalfunctions of the user device 100 and access both enterprise and personalresources 154. In particular, a user device 100 personal to a user ofthe user device 100 may be configured for additional enterprise use, forinstance, via through an enterprise bring-your-own-device (“BYOD”)deployment model. An enterprise may, for instance, employ a BYODresource-access model to lower the cost of providing its employees withaccess to enterprise functions and/or resources 154. Additionally, anenterprise may, for example, employ a BYOD resource-access model toprevent the need for an employee to carry an additionalenterprise-specific user device 100 to access enterprise functionsand/or resources 154. Functionality Watermarking and Management mayensure, amongst other benefits, that enterprise functions and/orresources 154 are not compromised when accessed by a user device 100with further access to personal functions and/or resources 154, and viceversa.

User device 100 may further store at least one watermark template 156 inthe data store 150. Watermark templates 156 may include an arrangementof data and/or a file containing such arranged data. In certainembodiments, watermark templates 156 may include description data, suchas data that describes the watermark templates 156 and/or other elementsassociated with the watermark templates 156, as described herein. Insome embodiments, watermark templates 156 may include configurationdata, such as data that configures the watermark templates 156 and/orother elements associated with the watermark templates 156, as describedherein.

In certain embodiments, watermark templates 156 may be associated withat least one of at least one function of the user device 100, at leastone resource 154 accessible to at least one function of at least oneuser device 100, at least one user device 100, at least one user of atleast one user device 100, and at least one enterprise. In particular,watermark templates 156 may be associated such that there is arelationship between the watermark templates 156 and the certainfunctions, resources 154, user devices 100, users of user devices 100,and enterprises. In some embodiments, an administrator, such as anadministrator of a watermark template server 220, may associate certainwatermark templates 156 with certain functions, resources 154, userdevices 100, users of user devices 100, and enterprises. As an example,an administrator of a watermark template server 220 may utilize aweb-based console application to specify certain watermark templates 156to associate with certain functions, resources 154, user devices 100,users of user devices 100, and enterprises.

Watermark templates 156 may include descriptive data elements thatdescribe functions of the user device 100, resources 154 accessible tothe functions of the user device 100, the user device 100, users of theuser device 100, and/or enterprises. In particular, descriptive dataelements may include one or more properties associated with suchfunctions of the user device 100, such resources 154 accessible to suchfunctions of the user device 100, such user devices 100, such users ofsuch user devices 100, and such enterprises. Additionally, watermarktemplates 156 may include one or more source identifiers describing acreator and/or distributor of the watermark templates 156, timestampsassociated with various actions performed with respect to the watermarktemplates 156, and locations associated with various actions performedwith respect to the watermark templates 156. As an example, descriptivedata elements may include statements indicating the identities of usersof user devices that have performed functions, the state of securitysettings on user devices that have performed functions, the time andlocation associated user devices that have performed functions, theownership by an enterprise of resources accessed by functions, and/orthe like.

Properties associated with functions of user devices 100 may include,for instance, at least one of prior functions performed on such userdevices 100, sensitivity levels of such functions of such user devices100, and/or security requirements associated with such functions of suchuser devices 100. In particular, properties associated with priorfunction performances may include a timestamp and location describingwhen and where a user device 100 last performed a camera function,properties associated with function sensitivity levels may identify thecamera function as “FOR CLASSIFIED USE ONLY,” and properties associatedwith function security requirements may include a requirement that asource identifier identifying a user device 100 and/or a user of a userdevice 100 that performs the camera function be captured upon the userdevice 100 performing the camera function.

Properties associated with resources 154 accessible to functions of userdevices 100 may include, for instance, at least one of prior functionsaccessing such resources 154, sensitivity levels of such resources 154,and/or security requirements associated with such resources 154, asdescribed herein. In particular, properties associated with priorfunctions accessing such resources 154 may identify an application on auser device 100 that last edited a resource 154, properties associatedwith resource 154 sensitivity levels may identify a resource 154 as“PRIVILEGED AND CONFIDENTIAL,” and properties associated with resource154 security requirements may include a requirement that a resource 154can only be accessed by a user device 100 while the user device 100 islocated at an enterprise facility associated with the resource 154.

Properties associated with user devices 100 may specify and/or describe,for example, at least one user device 100 identifier, user device 100hardware feature, user device 100 software feature, user device 100application, current time associated with such user devices 100, currentlocation associated with such user devices 100, and home locationassociated with such user devices 100. As an example, propertiesassociated with user devices 100 may include a listing of hardwarefeatures active on a user device 100 and/or accessible to a user device100 at a current time associated with the user device 100 and a currentlocation associated with a user device 100 at a current time associatedwith the user device 100. In particular, a current time associated witha user device 100 may be identified via the system clock of the userdevice 100, and a current location associated with a user device 100 maybe identified via a GPS sensor of the user device 100. Propertiesassociated with user device 100 may further include a determination ofwhether the user device 100 complies with at least one compliance rule158 based at least in part on a device profile 152 describing the stateof the user device 100, as described herein.

Properties associated with users of user devices 100 may include, forexample, at least one user identifier, user credential, user roleidentifier, enterprise identifier, current time associated with theuser, current location associated with the user, and home locationassociated with the user. User role identifiers may, for instance,specify a job title, job function, and/or the like describing the roleof the user with respect to an enterprise. Enterprise identifiers may,for example, specify an enterprise affiliated with a user, such as anenterprise that employs the user and/or provides resource 154 access tothe user. Current times associated with a user and current locationsassociated with a user may, for instance, specify a current time and/orcurrent location associated with the user device 100 associated with theuser. Home locations associated with a user may, for instance, specify aprimarily location of a user, such as a location where the user residesand/or a location where the user is employed.

Properties associated with an enterprise may include, for instance, atleast one facility location of the enterprise, phone number of theenterprise, employee of the enterprise, executive of the enterprise,business type of the enterprise, industry of the enterprise, and/orother data describing the enterprise. Furthermore, descriptive dataelements of a watermark template 156 may include at least one of asource identifier, a timestamp, and a location. A source identifier mayspecify, for instance, a user device 100, an administrator, and/or anenterprise associated with the creation of and/or modification of awatermark template 156. A timestamp may identify, for example, a timeand date when a watermark template 156 was created, modified and/orassociated. Similarly, a location may identify a geographic locationwhere a watermark template 156 was created, modified and/or associated.

Watermark templates 156 may include such descriptive data elements byvirtue of the association between the watermark templates 156 and suchfunctions of the user device 100, resources 154 accessible to thefunctions of the user device 100, the user device 100, users of the userdevice 100, or enterprises. In certain embodiments, watermark templates156 may include descriptive data elements that are populated based atleast in part on such functions of the user device 100, resources 154accessible to the functions of the user device 100, the user device 100,users of the user device 100, or enterprises. For example, watermarktemplates 156 may be populated by querying and/or analyzing thecharacteristics and/or state of such functions of the user device 100,resources 154 accessible to the functions of the user device 100, theuser device 100, users of the user device 100, or enterprises, asdescribed herein.

In certain embodiments, a watermark template 156 may include descriptivedata elements that are determined and/or identified at the time thewatermark template 156 is to be utilized and/or associated. Inparticular, a watermark template 156 may be dynamically composed suchthat the watermark template 156 includes dynamic descriptive dataelements that are accurate at the time the watermark template 156 isviewed, applied, and/or otherwise used by a user device 100. In someembodiments, a watermark template 156 may acquire dynamic descriptivedata elements with the assistance of a user device 100 communicativelycoupled to the watermark template 156, such as via an agent application250 and/or via an application programming interface communicativelycoupled to an operating system 115 of a user device 100.

Dynamic descriptive data elements may include and/or describe, forexample, a prior function performed on a user device 100 and/or prioraction taken on a resource 154, such as a prior creation, prior access,prior modification, prior storage, and prior transmission of a resource154 by a user device 100 and/or user of a user device 100. Atransmission of a resource 154 may, for instance, include transmittingthe resource 154 via a sharing feature, an email, an instant message, atext and/or multimedia message, a social media application, a FTPserver, and/or other means of transmitting resources 154 between userdevices 100. In some embodiments, a watermark template 156 may describesuch prior functions and/or actions by including descriptive dataelements detailing at least one user identifier, source identifier,timestamp, location, prior function and/or action type, contextualdetail describing such prior action, property associated with a userdevice 100 associated with such prior action. Timestamps may, forinstance, specify a date and/or time associated with the timestamp, suchas a date and time when a resource 154 was shared by a certain userdevice 100, a date and time when the resource 154 was received from thesharing user device 100 by a recipient user device 100, a date and timewhen a resource 154 was annotated and/or otherwise modified by a certainuser device 100, a date and time when a recipient user device 100 willcease to be authorized to perform actions on the resource 154, and/or adate and time when the resource 154 will expire and/or becomeinaccessible by user devices 100. A timestamp may further, for example,specify the context of the timestamp so as to describe the context ofsuch dates and/or times. Contextual details describing such prioractions may include, for example, whether the associated user device 100complied with at least one compliance rule 158 associated with suchprior functions and/or actions on a resource 154, as described herein.

Watermark templates 156 may further include descriptive data elementsthat are static and/or do not change with respect to a resource 154,user device 100, user of a user device 100, and/or function of a userdevice 100. In some embodiments, static descriptive data elements may bepre-configured by an administrator of a watermark template server 220,as described herein. Static descriptive data elements may, for instance,specify a sensitivity level associated with a certain function of a userdevice 100 and/or resource 154 associated with the respective watermarktemplate 156. Sensitivity levels associated with a function and/orresource 154 may specify that the function and/or resource 154 is atleast one of the following: confidential, proprietary, privileged, andmanaged. For example, a function of a user device 100 that capturesforensic evidence, such as a camera function and a microphone function,may be associated with a confidential sensitivity level and a privilegedsensitivity level. As another example, a resource 154 that containsfinancial data may be associated with both a confidential sensitivitylevel and a proprietary sensitivity level.

A confidential sensitivity level may, for example, indicate that therespective function and/or resource 154 is the confidential property ofan enterprise associated with the function and/or resource 154. Aproprietary sensitivity level may, for instance, indicate that thefunction and/or resource 154 constitutes the intellectual property of anenterprise associated with the function and/or resource 154. Aprivileged sensitivity level may, for instance, indicate that therespective function and/or resource 154 is subject to and/or protectedby an attorney-client relationship and/or the work product doctrine. Amanaged sensitivity level may, for example, indicate that the respectivefunction and/or resource 154 is managed and/or controlled by a resourceserver 210, as described herein. More particularly, a managedsensitivity level may describe an enterprise and/or business that ownsand/or controls the respective function and/or resource 154, which mayalso own and/or control a resource server 210 associated with and/orcommunicatively coupled to the respective resource 154.

Static descriptive data elements may also, for instance, specify asecurity requirement associated with a certain function and/or resource154 associated with the respective watermark template 156. Securityrequirements may specify, for instance, certain authorized and/orunauthorized user identities, device identities, device hardwarefeatures, device software features, device applications, functionperformance times and/or durations, and function performance locations.In other words, security requirements may specify positive and negativecriteria required for a certain user device 100 to perform a certainaction on a resource 154 associated with such security requirements. Forinstance, a function of a user device 100, such as a camera function,may only be authorized during workday hours according to an enterprisesecurity policy, which may be reflected by static descriptive dataindicating that the camera function is prohibited outside workday hours.In some embodiments, user identities and device identities may includeuser identifiers and device identifiers, respectively. In certainembodiments, security requirements are expressed and/or enforced viacompliance rules 158 associated with one or more user devices 100subject to the security requirements, as described herein.

In certain embodiments, watermark templates 156 may be configured suchthat, when applied to a function of a user device 100, the watermarktemplates 156 are overlaid onto a graphical interface associated withthe function of the user device 100. Additionally, watermark templates156 may be configured such that, when applied to a function of a userdevice 100, the watermark templates 156 are added to at least oneposition within a graphical interface associated with the function ofthe user device 100. In some embodiments, watermark templates 156 may beconfigured such that, when applied to a resource 154 accessible to afunction of a user device 100, the watermark templates 156 are overlaidonto the resource 154. Moreover, watermark templates 156 may beconfigured such that, when applied to a resource 154 accessible to afunction of a user device 100, the watermark templates 156 are added toat least one position within the resource 154.

In particular, watermark templates 156, and/or data contained therein,may be added to at least one of a header of the resource 154, a body ofthe resource 154, a footer of the resource 154, a structural metadata ofthe resource 154, a descriptive metadata of the resource 154, and awrapper encapsulating the resource 154. Structural metadata, which maynot be visible to a viewer of a resource 154, may define the manner inwhich an applicable resource 154 must be named according to a namingconvention element and must be stored according to a storage structureconvention element. Descriptive metadata, which also may not be visibleto a viewer of a resource 154, may describe the resource 154 accordingto the traits discussed herein. Wrappers encapsulating a resource 154may include a security layer surrounding the resource 154, which mayprotect the underlying resource 154 from certain actions being taken onthe resource 154, such as forwarding the resource 154 to an unauthorizedrecipient.

As an example, a watermark template 156 may include a collection ofdescriptive data elements and may be configured to add each of thecollection of descriptive data elements to specific positions within afunction of the user device 100 and/or a resource 154 accessible to afunction of the user device 100 when the watermark template 156 isapplied to the function and/or resource 154. More specifically, thewatermark template 156 may include a name of an enterprise associatedwith the function and/or resource 154 and may be configured to add theenterprise name to the upper left corner of the function and/or resource154 when the watermark template 156 is applied to the function and/orresource 154. The watermark template 156 may further include a currenttimestamp associated with a user device 100 requesting to perform thefunction and/or access the resource 154 and may be configured to add thecurrent timestamp to the lower left hand corner of the watermarktemplate 156 when the watermark template 156 is applied to the functionand/or resource 154. The watermark template 156 may yet further includea statement of confidentiality and may be configured to add theconfidentiality statement to a certain function and/or resource 154 intranslucent font diagonally across the length of the function and/orresource 154 when the watermark template 156 is applied to the functionand/or resource 154.

Furthermore, watermark templates 156 may further include configurationdata elements. In certain embodiments, configuration data elements mayconfigure watermark templates 156 and/or other elements associated withwatermark templates 156, such as functions of user devices 100 and/orresources 154 accessible to functions of user devices 100.

In some embodiments, configuration data may configure descriptive dataelements included in watermark templates 156, which may be associatedwith functions of user devices 100 and/or resources 154 accessible tofunctions of user devices 100. Configuration data elements may, forinstance, specify where to position descriptive data elements within thewatermark templates 156. Configuration data elements may further specifya textual formatting schema to apply to descriptive data elementsincluded in watermark templates 156. As an example, configuration dataelements of a watermark template 156 may specify that the name of anenterprise included in the watermark template 156 should be placed inthe upper left hand corner and should be formatted in red colored, boldstyle, size 18 Times New Roman font. Consequently, upon associating sucha watermark template 156 with a camera function of a user device 100,resources 154 created by such camera function may thereafter have thename of the enterprise overlaid onto such resources 154 in the upperleft hand corner of the resources 154 in red colored, bold style, size18 Times New Roman font.

In some embodiments, configuration data may also configure functions ofuser devices 100 and/or resources 154 accessible to functions of userdevices 100. Configuration data may, for example, specify a namingconvention to apply to functions and/or resources 154. In particular,configuration data of a watermark template 156 may specify that a camerafunction of a user device 100 that is associated with the watermarktemplate 156 must name any resources 154 created by the camera function,such as photograph resources 154 and/or video resources 154, accordingto a naming convention that includes the name of an enterprise, atimestamp, and a location where the resources 154 were created. As anexample, a timestamp and location may be determined at the time thecamera function is performed by the user device 100 by querying thedevice profile 152 of the user device 100 to determine the current dataand time associated with the user device 100 and the current locationassociated with the user device 100.

As an example, configuration data elements of a watermark template 156may specify that a camera function of a user device 100 that isassociated with the watermark template 156 must name any resources 154created by the camera function, such as photograph resources 154 and/orvideo resources 154, according to a naming convention that includes thename of an enterprise, a timestamp, and a location where the resources154 where created. In particular, a timestamp and location may bedetermined at the time the camera function is performed by the userdevice 100 by querying the device profile 123 of the user device 100 todetermine a current date associated with the user device 100, a currenttime associated with the user device 100, and a current locationassociated with the user device 100.

Configuration data of watermark templates 156 may also, for instance,include a storage structure convention element that should be applied tofunctions of user devices 100 and/or resources 154 accessible to userdevices 100 that are associated with the respective watermark templates156. In certain embodiments, a storage structure convention element mayspecify at least one storage location where a user device 100 shouldstore certain functions of the user device 100 and/or certain resources154 accessible to certain functions of the user device 100. Inparticular, storage locations of storage structure convention elementsmay include at least one of certain memories of a user device 100 and/ora remote server, certain drives within certain memories, and certainfolders within certain memories where a user device 100 should storefunctions of the user devices 100 and/or resources 154 accessible tofunctions of the user devices 100 that are associated with therespective watermark templates 156. In some embodiments, storagestructure convention elements may specify at least one file type inwhich a user device 100 should store certain functions of the userdevice 100 and/or certain resources 154 accessible to certain functionsof the user device 100. As an example, file types of storage structureconvention elements may specify that resources 154 captured by amicrophone function of a user device 100 that is associated with therespective watermark templates 156, such as voice recording files, mustbe stored in a digital rights management file format, must be encryptedusing AES-256 encryption, and must be limited to a file size of under 1MB to avoid excessive data network-related charges.

In certain embodiments, configuration data of watermark templates 156may add functionality to and/or remove functionality from functions ofthe user device 100 and/or resources 154 accessible to the functions ofthe user device 100. Configuration data of watermark templates 156 may,for instance, add functionality buttons to a graphical interface of afunction of the user device 100, which may add additional functionalityto the functions provided by the function of the user device 100. As anexample, a “camera controls” set of buttons may be added to a camerafunction of the user device 100 by applying a watermark template 156 tothe camera function that includes configuration data for the “cameracontrols” set of buttons. As another example, a “media bar” may be addedto a resource 154 created by a camera function of the user device 100that allows a user of the user device 100 to quickly navigate to otherresources 154 created by the camera function of the user device 100.Configuration data may also, for example, remove functionality from afunction of the user device 100 by removing functionality buttons from agraphical interface of the function of the user device 100, which mayprevent performance of certain functions of the user device 100.Configuration data of watermark templates 156 may further, for instance,be applied to functions and/or resources 154 that include effectivedate-constrained certificates and/or cryptographic keys to prevent userdevices 100 from accessing the functions and/or resources 154 beyond theeffective date.

While watermark templates 156 may comprise visible indicators such asdescriptive data elements, watermark templates 156 need not comprisevisible indicators. In certain embodiments, a watermark template 156 maybe configured to match the formatting of the function of the user device100 and/or resource 154 to which the watermark template 156 is applied,where such formatting is non-visible in nature. For example, an audiowatermark template 156 may be applied to a microphone function of a userdevice 100, where the audio watermark template 156 comprises aconfigurable message concatenated onto the audio resource 154 at thebeginning of the existing audio, within the existing audio, and/or atthe end of the existing audio of the audio resource 154. Additionally,an audio watermark template 156 may be applied to an audio resource 154,where the audio watermark template 156 comprises an audio marker thatmay be heard concurrently with the existing audio of the audio resource154. Such an audio watermark template 156 may comprise a spoken audioand/or a non-spoken audio, such as a public domain, trademarked and/orcopyrighted musical selection associated with an enterprise associatedwith the watermark template 156.

In some embodiments, a watermark template 156 may include symbols,letters, and/or numbers that may be visible to an individual but may notrepresent any recognizable message in combination with one another. Forinstance, a watermark template 156 may be configured to translatecertain descriptive data from a format that may be recognizable to anindividual into a format that may not be recognizable to the individual,such as translating a user identifier from “John Doe” to “62s3 89f.” Asanother example, a watermark template 156 may be configured tosystematically place certain symbols, letters, and/or numbers amongst afunction of a user device 100 and/or resource 154 accessible to afunction of a user device 100 when applied to the function and/orresource 154 such that the symbols, letters and/or numbers may only bedeciphered with the assistance of a key specific to the systematicplacement.

Furthermore, in certain embodiments, a watermark template 156 may bevisible in nature but may not be recognizable to an individual due tothe scale of the watermark template 156 in comparison to a function ofthe user device 100 and/or a resource 154 accessible to a function ofthe user device 100 to which the watermark template 156 is applied. Awatermark template 156 and/or data included therein may be, for example,either extremely small or extremely large in comparison to a functionand/or resource 154, such that watermark template 156 cannot berecognized when applied to the function and/or resource 154. Inparticular, descriptive data of a watermark template 156 may be appliedto a function and/or resource 154 in a very small font such that thefont cannot be seen amongst the pixels of the function and/or resource154 without magnifying the function and/or resource 154.

In some embodiments, a watermark template 156 may be and/or include atangential addition to a function of a user device 100 and/or a resource154 such that the function and/or resource 154 remains visuallyidentical to before the watermark template 156 was applied to thefunction and/or resource 154. For instance, the watermark template 156may be and/or include metadata, an xml description, a file header, afile property, a function performance summary, a resource 154 changesummary and/or the like that may be tangentially added to a function ofa user device 100 and/or a resource 154 without altering the visibleaspects of the function and/or resource 154. As an example, anannotation watermark template 156 may be added to an annotation functionof a user device 100, which may include a non-visible change historythat describes all annotations made with respect to resources 154annotated by the annotation function of the user device 100 over thelifespan of the resources 154. For instance, a resource 154 annotated byan annotation feature of a user device 100 may be modified to include animage-based change summary that captures at least one of an initialstate, a previous state, and/or a current state of the resource 154,which may be added to the resource 154 as soon as the annotation of theresource 154 is completed by the user device 100 and/or as a part of theannotation of the resource 154 by the user device 100. An image-basedchange history may be embodied, for instance, in a QR code and/or MD5hash to condense the change summary into a small image, which might beeven further reduced in size depending on a pixel resolution of theparticular resource 154 and a configurable required rendering qualityfor the change summary and/or particular resource 154.

In certain embodiments, user devices 100 may apply watermark templates156 to certain functions of the user device 100 and/or certain resources154 accessible to certain functions of the user device 100. As a highlevel example and described herein, an administrator may specify awatermark template 156 to apply to a function of a user device 100, suchas a camera function. The watermark template 156 may be applied to thecamera function via a compliance rule 158, which may specify that a userdevice 100 may only be authorized to perform the camera function whilethe watermark template 156 is applied to the camera function. Thecompliance rule 158 may be triggered, for instance, when the user device100 identifies a request to perform the camera function, such as when auser of the user device 100 launches a camera application on the userdevice 100. In order to maintain a state of compliance with thecompliance rule 158, the user device 100 may apply the watermarktemplate 156 to the camera function of the user device 100 in a mannerspecified by the compliance rule 158. For instance, the user device 100may overlay the watermark template 156 onto a graphical interfaceassociated with the camera function and add the watermark template 156to any photograph resources 154 created by the camera function. In someembodiments, the watermark template 156 may identify the owner of theuser device 100 such that the photograph resources 154 created by thecamera function may be visually identified as owned by the owner of theuser device 100 via the watermark template 156.

As described herein, a watermark template 156 may be overlaid ontoand/or added to a function of the user device 100 and/or a resource 154accessible to a function of the user device 100, such that the watermarktemplate 156 and the function and/or resource 154 are united when viewedby an individual. For example, a resource 154 may be modified such thata plurality of descriptive text of a watermark template 156 may bevisible on the resource 154. Furthermore, the function and/or resource154 may appear largely the same as before the watermark template 156 isoverlaid onto and/or added to the function and/or resource 154, as thewatermark template 156 may include a translucent body and/or backgroundthat may allow the underlying function and/or resource 154 to remainvisible amongst the data included within the watermark template 156.

In certain embodiments, a function and/or resource 154 may be markedand/or badged with “Watermarked” and/or the like to indicate that awatermark template 156 is applied to the function and/or resource 154.Similarly, a function and/or resource 154 may be marked and/or badgedwith indicia of an action that triggered a watermark template 156 to beapplied to such function and/or resource 154 via a compliance rule 158,such as by placing a diagonal badge across the upper left corner of anicon of the function and/or resource 154 stating “Shared” to indicatethat the function and/or resource 154 was watermarked in response theresource 154 being shared with another user device 100. For instance, anicon representing the function and/or resource 154 may be marked and/orbadged to indicate that the function and/or resource 154 was watermarkedupon being shared.

In some embodiments, the manner in which a user device 100 associates awatermark template 156 with a resource 154 may be based at least in parton the type of resource 154 that will be associated with the watermarktemplate 156. For example, an image resource 154 may have a watermarktemplate 156 superimposed on the image resource 154 such that thewatermark template 156 and the underlying image are concurrentlyvisible, as described herein. As another example, an email resource 154may have a watermark template 156 displayed as an overlay and/orunderlay to the email resource 154 and/or the watermark template 156 maybe included as a header and/or signature to the email resource 154. As afurther example, a word processing, spreadsheet and/or presentation(“productivity”) resource 154 may comprise a watermark template 156 inat least one of the following: displayer in a header and/or footersection of the productivity resource 154, incorporated as visible and/ornon-visible metadata in the productivity resource 154, and/or displayedas an overlay, underlay, and/or adjacent image to at least a portion ofthe content of the productivity resource 154. In some embodiments, awatermark template 156 may be repeated so as to be visible and/oraffixed in at least one of the above manners on each page, slide,worksheet, etc. of the productivity resource 154.

In certain embodiments, a watermark template 156 may be permanentlyapplied to a function of the user device 100 and/or a resource 154accessible to a function of the user device 100. For example, a functionand/or resource 154 may be permanently modified such that descriptivetext of a watermark template 156 cannot be removed from the functionand/or resource 154. Furthermore, a series of watermark templates 156may be applied to a function and/or resource 154 over the lifespan ofthe function and/or resource 154, such that a watermark template 156 isapplied to a function and/or resource 154 with one or more previouslyapplied watermark templates 156. For instance, watermark templates 156may be applied to functions and/or resources 154 according to aplurality of compliance rules 158, as described herein, such that awatermark template 156 is applied to the functions and/or resources 154upon certain actions being taken with respect to the functions and/orresources 154. More specifically, a watermark template 156 may beapplied to a resource 154 each time a user device 100 seeks to share theresource 154, where the applied watermark template 156 may bedynamically populated based on a current context, including a currentlocation, a current timestamp and a device identifier associated withthe request to share the resource 154.

Some descriptive data elements included in a watermark template 156 maybe static, such as the title of a resource 154 and a current timestampassociated with an initial creation of the resource 154, and may,therefore, remain the same each time the watermark template 156 isapplied to a function of the user device 100 and/or a resource 154accessible to a function of the user device 100. However, somedescriptive data elements included in a watermark template 156 may bedynamic, such as a property associated with a user device 100, and maytherefore be updated each time the watermark template 156 is applied toa function and/or a resource 154. For instance, the watermark template156 may be updated upon each application with a function and/or resource154 based at least in part on a device profile 152 of the user device100.

In some embodiments, a function of the user device 100 and/or a resource154 accessible to a function of the user device 100 may include manywatermark templates 156 that were previously applied to the functionand/or resource 154. The function and/or resource 154 may therebyinclude a comprehensive set of data that continues to increase over thelifespan of the function and/or resource 154, as each additionalwatermark template 156 applied to the function and/or resource 154 mayincrease the comprehensive set of data applied to the function and/orresource 154. In particular, a function and/or resource 154 may belayered with many watermark templates 156 and may thereby provide ahistory of the resource 154. For instance, a resource 154 may includedescriptive data elements of a first watermark template 156 after thefirst watermark template 156 is applied to the resource 154, theresource 154 may include descriptive data elements of the firstwatermark template 156 and descriptive data elements of a secondwatermark template 154 after the second watermark template 156 isapplied to the resource 154, and so on. Alternatively, in someembodiments, a function and/or resource 154 may only include a newlyapplied watermark template 156, as previously applied watermarktemplates 156 may be removed from the function and/or resource 154 uponapplying a new watermark template 156.

Moreover, user device 100 may store one or more compliance rules 158.Compliance rules 158 may be associated with at least one of certain userdevices 100, certain users of user devices 100, and certain resources154. For instance, compliance rules 158 may be associated with certainresources 154 when certain users of certain user devices 100 requestand/or initiate certain actions on such resources 154, such as when acertain employee using a certain tablet seeks to email certain documentsto certain recipients that are not affiliated with the respectiveenterprise. Compliance rules 158 may be associated with such userdevices 100, users of user devices 100, and/or resources 154 by anadministrator of a compliance rule server 230, as described herein.

Compliance rules 158 may specify security requirements, conditionsand/or events required for user device 100 to perform certain functionson user device 100. In some embodiments, compliance rules 158 mayspecify certain methods and/or steps of methods that must be performedbefore a user device 100 is authorized to perform certain functions ofthe user device 100 and/or access certain resources 154. In particular,compliance rules 158 may specify that certain watermark templates 156must be applied to certain functions of a user device 100 for the userdevice 100 to gain authorization to perform the functions of the userdevice 100. Similarly, compliance rules 158 may specify that certainwatermark templates 156 must be applied to certain resources 154accessible to certain functions of a user device 100 for the user device100 to gain authorization to access the resources 154 and/or perform thefunctions.

In some embodiments, compliance rules 158 may specify that user device100 must satisfy and/or comply with a single condition for user device100 to be authorized to perform certain functions of user device 100and/or access certain resources 154 associated with the compliance rules158. For instance, compliance rules 158 may require that user device 100is associated with a current time that is within an authorized timeperiod specified by such compliance rules 158 in order for user device100 to be authorized to perform certain functions and/or access certainresources 154. More specifically, compliance rules 158 may specify thatuser device 100 is authorized to share a business email resource 154,such as by email, while the system clock of user device 100 is within aconfigured workday and user device 100 is not authorized to access thebusiness email resource 154 while the system clock of user device 100 isoutside of the configured workday. In some embodiments, compliance rules158 may specify that user device 100 must satisfy and/or comply withmore than one condition for user device 100 to be authorized to performcertain functions and/or access certain resources 154. For example,compliance rules 156 may specify that user device 100 must be associatedwith a “safe zone” location, such as an enterprise office location, toupload certain sensitive resources 154 accessible to user device 100,such as those affiliated with an enterprise, which may require that botha GPS sensor of user device 100 indicates that user device 100 iscurrently located within the geographic boundaries of the safe zone andthat a Wi-Fi sensor of user device 100 indicates that user device 100 iscommunicatively coupled to a Wi-Fi network access point associated withthe safe zone.

In some embodiments, compliance rules 158 may specify that user device100 and another computing device, such as another user device 100, mustboth satisfy and/or comply with one or more conditions for user device100 to be authorized to perform certain functions of user device 100and/or access certain resources 154. Compliance rules 158 may requirethat user device 100 be located within proximity of and/or becommunicatively coupled to a secondary user device 100 and that bothuser devices 100 be located within an authorized location in order toperform certain functions and/or access certain resources 154. As anexample, compliance rules 158 may specify that user devices 100associated with nurses may only access resources 154 associated withtheir patients, such as a patient's medical records, while the userdevices 100 associated with such nurses are located within 10 feet ofuser devices 100 associated with such patients and while the userdevices 100 associated with nurses and user devices 100 associated withpatients are both located within examination rooms reserved for suchpatients' appointments.

In certain embodiments, compliance rules 158 may be granular such thatthe user device 100 may be authorized to perform certain functionsand/or access certain resources 154 depending on how many of theconditions of the compliance rules 158 are satisfied by user device 100.For example, user device 100 may be authorized to access an enterprisecontact resource 154 on user device 100 if a GPS sensor on user device100 indicates that user device 100 is located within the enterprise'slocation, but user device 100 may be prohibited from sending an emailwith an enterprise resource 154 attached to the email until a certainwatermark template 156 is applied to the enterprise resource 154 anduntil it is confirmed that the user device 100 is located within a “safezone” by being communicatively coupled to a Wi-Fi network access pointassociated with the enterprise.

In some embodiments, an agent application 250 (“agent app”) on the userdevice 100 may determine whether compliance rules 158 are satisfied bythe user device 100, as described herein. For instance, an agentapplication 250 may determine whether user device 100 complies withcertain compliance rules 158 by determining whether device profile 152provides indications that user device 100 complies with such compliancerules 156. As an example, an agent application 250 may determine whetherdevice profile 152 specifies that the current time associated with userdevice 100 is within a configured workday specified by compliance rules158. Alternatively, the user device 100 may transmit all and/or aportion of device profile 152 to a compliance server 230, which maydetermine whether user device 100 satisfies the compliance rules 158.

In any case, the user device 100 may be authorized and/or instructed toperform functions of user device 100 and/or access certain resources 154in response to a determination that the user device 100 complies withthe compliance rules 158. In certain embodiments, an agent application250 may authorize requests by the user device 100 to perform functionsand/or access resources 154 by transmitting instructions to theoperating system 115 of user device 100 and/or communicating with suchoperating system 115 via an API and/or SDK. In some embodiments, acompliance server 230 may authorize requests by the user device 100 toperform functions and/or access resources 154 by transmittinginstructions to the operating system 115 of user device 100 and/orcommunicating with such operating system 115 via an API and/or SDK.

Furthermore, embodiments of this disclosure may be practiced inconjunction with a graphics library, other operating systems, or anyother application program and is not limited to any particularapplication or system. The devices described with respect to the Figuresmay have additional features or functionality. For example, user device100 may also include additional data storage devices (removable and/ornon-removable) such as, for example, magnetic disks, optical disks, ortape (not shown).

FIG. 2 is a block diagram view of an operating environment 200 showingother elements operating with the user device 100, such as a network240, resource server 210, watermark template server 220, and complianceserver 230. In some embodiments, the user device 100 may include and/orexecute at least one of the following: an agent app 250, a web browser252, an email client 254, and a secure application 256. The agent app250 may comprise, for instance, an application communicatively coupledto at least one of the resource server 210, watermark template server220, and compliance server 230 so as to enable such servers to instructthe user device 100 to perform certain actions on the user device 100,such as take certain actions on certain resources 254, associate certainwatermark templates 156 with certain resources 254, and conform itsoperations to certain configuration profiles 158. The web browser 252may comprise, for example, an application communicatively coupled to thenetwork 240 that is capable of at least one of the following: viewingwebsites, downloading resources from web servers, uploading resources154 to web servers, executing web applications, and/or the like. Theemail client 254 may comprise, for instance, an applicationcommunicatively coupled to the network 240 that is capable of sendingemail resources 154, receiving email resources 154, scheduling calendarresources 154, storing contact resources 154 and/or other operationsprovided by personal information managers (“PIM's”). Furthermore, thesecure app 256 may comprise, for instance, a containerized resourceapplication that is capable of receiving resources 154, storing theresources 154 within the container to protect the resources 154 fromaccess attempts by other applications on the user device 100, andprovide access to the resources 154 in accordance with and/or incompliance with compliance rules 158 associated with the resources 154.

In certain embodiments, the agent app 250, web browser 252, email client254, and secure app 256 may be configured to create event logs thatdetail operations carried out by the agent app 250, web browser 252,email client 254, and secure app 256. In particular, event logs maycapture each application's operations with respect to performance offunctions of the user device 100, access to resources 154, applicationof watermark templates 156 to functions and/or resources 154 over thelifespan of the functions and/or resources 154, and the user device's100 compliance with applicable compliance rules 158. The agent app 250,web browser 252, email client 254, and secure app 256 may be furtherconfigured to transmit event logs to at least one of the resource server210, watermark template server 220, and compliance server 230, which maybe utilized by each server in its execution of management systems and/orapplications associated with the user device 100. More specifically, theuser device 100 may transmit event logs to servers executing at leastone of an enterprise mobility management service, a mobile devicemanagement service, a mobile content management service, a mobileapplication management service, and a mobile email management service.

In some embodiments, the user device 100 may be communicatively coupledto the resource server 210, watermark template server 220, andcompliance server 230 via the network 240. The network 240 may include,for instance, a cellular network, Wi-Fi network, Bluetooth network,and/or any other network capable of transmitting data between and/oramongst user device 100, resource server 210, watermark template server220, and compliance server 230. While the resource server 210, thewatermark template server 220, and the compliance server 230 arerepresented as separate elements amongst operating environment 200, itis understood that such servers could be combined into a single servercapable of performing the same and/or similar functionality that each ofthe resource server 210, the watermark template server 220, and thecompliance server 230 may be capable of performing separately, such asexecuting a management system and/or application.

In some embodiments, the resource server 210 may comprise a server thatmanages a plurality of resources 154, such as resources 154 associatedwith an enterprise. The resource server 210 may include a resource store212, which may store such resources 154. The resource server 210 maytransmit resources 154 to the user device 100 and may receivetransmissions of resources 154 from the user device 100 via the network240. The resource server 210 may be associated with the user device 100,for instance, by enrolling the user device 100 into a management systemand/or application executed by resource server 210. More specifically,resource server 210 may distribute certain settings and/or configurationprofiles to the user device 100 that enables resource server 210 toinstruct user device 100 to perform certain functions, such asinstructing user device 100 to download certain resources 154 fromresource store 212 of resource server 210. The resource server 210 mayalso track and/or manage access to resources 154 associated with theresource server 210, such as by receiving event logs transmitted by userdevice 100 and/or recording accesses to the resources 154. The eventlogs may include and/or describe usage of the resource 154 by detailing,for instance, a device identifier associated with a user device 100, auser identifier associated with a user of a user device 100, a resource154, a watermark template 156 associated with a resource 154, an requestto perform an action on a resource 154, an action performed on aresource 154, and/or the like.

In some embodiments, the watermark template server 220 may comprise aserver that manages a plurality of watermark templates 156. Thewatermark template server 220 may include a watermark template store222, which may store such watermark templates 156. The watermarktemplate server 220 may transmit watermark templates 156 to the userdevice 100 via the network 240. The watermark template server 220 mayalso receive transmissions of resources 154 with watermark templates 156applied to the resources 154 from the user device 100. The watermarktemplate server 220 may be associated with the user device 100, forinstance, by enrolling the user device 100 into a management systemand/or application executed by watermark template server 220. Morespecifically, watermark template server 220 may distribute certainsettings and/or configuration profiles to the user device 100 thatenables watermark template server 220 to instruct user device 100 toperform certain functions, such as instructing user device 100 todownload certain watermark templates 156 from watermark template store222 of watermark template server 220 and/or to apply certain watermarktemplates 156 to certain functions of the user device 100 and/orresources 154 accessible to functions of the user device 100. Thewatermark template server 220 may also track and/or manage the usage ofwatermark templates 156 associated with the watermark template server220, such as by receiving event logs transmitted by user device 100and/or recording accesses to the watermark templates 156. The event logsmay include and/or describe usage of the watermark templates 156 bydetailing, for instance, a device identifier associated with a userdevice 100, a user identifier associated with a user of a user device100, a request to perform a function on the user device 100 and/oraccess a resource 154, an function performed and/or a resource 154accessed, a watermark template 156 applied to a function and/or resource154, etc.

In some embodiments, the compliance server 230 may comprise a serverthat manages a plurality of compliance rules 158. The compliance server230 may include a compliance rule store 232, which may store suchcompliance rules 158. The compliance server 230 may transmit compliancerules 158 to the user device 100 and may receive transmissions ofcompliance audits and/or device profiles 152 that may be used todetermine whether the user device 100 complies with compliance rules 158from the user device 100 via the network 240. The compliance server 230may be associated with the user device 100, for instance, by enrollingthe user device 100 into a management system and/or application executedby compliance server 230. More specifically, compliance server 230 maydistribute certain settings and/or configuration profiles to the userdevice 100 that enable the compliance server 230 to instruct the userdevice 100 to perform certain functions of the user device 100 and/oraccess certain resources 154. As an example, compliance rules 158 may betransmitted from a compliance server 230 to a user device 100 toinstruct an agent application 250 on the user device 100 to determinewhether the user device 100 complies with certain compliance rules 158based on the device profile 152 associated with the user device 100before authorizing the user device 100 to perform certain functions ofthe user device 100 and/or access certain resources 154 accessible tocertain functions of the user device 100. The compliance server 230 mayalso track and/or manage the usage of compliance rules 158 associatedwith the compliance server 320, such as by receiving event logstransmitted by user device 100 and/or recording compliancedeterminations with respect to the compliance rules 158.

FIG. 3 is a flow chart setting forth the general stages involved in amethod 300 consistent with embodiments of this disclosure for providingfunctionality watermarking and management. Method 300 may be implementedusing element(s) of operating environment 200, such as user device 100,resource server 210, watermark template server 220, compliance server230, and network 240, as described above. Ways to implement the stagesof method 300 will be described in greater detail below.

Method 300 may begin at starting block 305 and proceed to stage 310where a request to perform at least one function of a user device 100 isidentified. Requests to perform functions of the user device 100 mayinclude, for instance, requests to perform hardware functions, softwarefunctions, and/or applications executed by the user device 100. Incertain embodiments, an agent application 250 on a user device 100 maymonitor the operations of the user device 100 to identify requests toperform functions of the user device 100. For instance, an agentapplication 250 may identify requests transmitted by hardware functions,software functions and/or applications executed by the user device 100to an operating system 115 of the user device 100, which may request theoperating system 115 to perform certain functions of the user device 100that are controlled by the operating system 115 of the user device 100.Additionally, an agent application 250 may identify requests transmittedby hardware functions, software functions and/or applications executedby the user device 100 to a service communicatively coupled to the userdevice 100, such as a resource server 210, a watermark template server220, or a compliance server 230. In some embodiments, a servicecommunicatively coupled to the user device 100 may identify requeststransmitted by the user device 100 to such service to identify requestsby the user device 100 to perform functions of the user device 100.

From stage 310, method 300 may advance to stage 315 where at least onewatermark template 156 is identified. In certain embodiments, watermarktemplates 156 may be identified that are associated with at least one ofthe identified functions of the user device 100, resources 154accessible to identified functions of the user device 100, the userdevice 100, a user of the user device 100, and an enterprise. In someembodiments, an administrator of a watermark template server 220 mayassociate a watermark template 156 with certain functions of the userdevice 100, resources 154 accessible to identified functions of the userdevice 100, user devices 100, users of user devices 100, and enterprisesbased on an affiliation between the watermark template 156 and thefunctions of the user device 100, resources 154 accessible to identifiedfunctions of the user device 100, user devices 100, users of userdevices 100, and enterprises. As an example, the data store 150 of theuser device 100 may be searched and/or queried to identify watermarktemplates 156. As another example, a watermark template store 222 withina resource server 220 communicatively coupled with the user device 100may be searched and/or queried to identify watermark templates 156.

From stage 315, method 300 may advance to stage 320 where the identifiedwatermark templates 156 are applied to the identified functions of theuser device 100. In certain embodiments, watermark templates 156 may beapplied to the functions of the user device 100 by overlaying thewatermark templates 156 onto at least one graphical interface associatedwith the functions of the user device 100. Also, watermark templates 156may be applied to resources 154 accessible to functions of the userdevice 100 by overlaying the watermark templates 156 onto the resources154. In particular, watermark templates 156 may be applied to resources154 created by the identified functions of the user device 100, modifiedby the identified functions of the user device 100, stored by theidentified functions of the user device 100, and/or transmitted by theidentified functions of the user device 100. More particularly,resources 154 transmitted by the user device 100 may include resources154 emailed, instant messaged, text messaged, uploaded or transmittedvia a file transfer within the user device 100, to another user device100, and/or to a service communicatively coupled to the user device 100.

In some embodiments, watermark templates 156 may be applied to thefunctions of the user device 100 by adding the watermark templates 156to at least one graphical interface associated with the functions of theuser device 100 in at least one position within the graphical interface.Additionally, watermark templates 156 may be applied to resources 154accessible to functions of the user device 100 by adding the watermarktemplates 156 to the resources 154 in at least one position within theresources 154. In certain embodiments, watermark templates 156 may beadded resources 154 accessible to functions of the user device 100 in atleast one of the a header of the resource 154, a footer of the resource154, a structural metadata element of the resource 154, a descriptivemetadata element of the resource 154, and a wrapper encapsulating theresource 154. In any case, watermark templates 156 may be positionedwithin the functions of the user device 100 and/or resources 154accessible to functions of the user device 100 over the lifespan of thefunctions and/or resources 154 according to a pre-defined placementalgorithm and/or sequence, such that multiple watermark templates 156may be applied to a single function and/or resource 154 withoutoverwriting previously applied watermark templates 156.

From stage 320, method 300 may advance to stage 325 where the identifiedrequests to perform functions of the user device 100 are authorized. Incertain embodiments, the identified requests to perform the functions ofthe user device 100 may only be authorized while the identifiedwatermark templates 156 are applied to the respective functions of theuser device 100. In some embodiments, the authorization of theidentified requests to perform the functions of the user device 100 mayoccur concurrently with the application of the identified watermarktemplates 156 to the respective functions of the user device 100. Uponcompleting the authorization step of stage 325, the method 300 may endat stage 330.

In certain embodiments, requests to perform functions of the user device100 may be authorized by instructing the user device 100 that therequest is authorized and/or by instructing the user device 100 toperform the requested at least one function. In some embodiments,requests to perform functions of the user device 100 may be authorizedby permitting the user device 100 to perform the at least one functionwithout interference, such as by taking no action. As an example, anagent application 250 may transmit commands to the operating system 115of the user device 100 via an API that specify that the user device 100should authorize the request to perform the functions of the user device100. Additionally, a compliance server 230 may transmit commands to theuser device 100, and/or functions of the user device 100, that specifythat the user device 100 should authorize the request to perform thefunctions of the user device 100.

In some embodiments, requests to perform the functions of the userdevice 100 may only be authorized while the user device 100 complieswith at least one compliance rule 158. As an example, an agentapplication 250 may determine whether the user device 100 complies withthe compliance rules 158, which may be determined based on a deviceprofile 152 of the user device 100 describing the state of the userdevice 100. Additionally, a compliance server 230 may receive a deviceprofile 152, or data contained therein, and determine whether the userdevice 100 complies with the compliance rules 158, which may be storedwithin the compliance rule store 232. In any case, requests to performfunctions of the user device 100 may be denied if it is determined thatthe user device 100 does not comply with the compliance rules 158.

In certain embodiments, requests to perform functions of the user device100 may be denied by instructing the user device 100 that the request isnot authorized and/or by instructing the user device 100 not to performthe requested function. In some embodiments, requests to performfunctions of the user device 100 may be denied by preventing the userdevice 100 from performing the requested function, such as bytransmitting commands to the user device 100 that specify that the userdevice 100 should delete data from storage locations associated with thefunction of the user device 100. As an example, an agent application 250may transmit commands to the operating system 115 of the user device 100via an API that specify that the user device 100 should deny the requestto perform the identified functions of the user device 100.Additionally, a compliance server 230 may transmit commands to the userdevice 100, and/or functions of the user device 100, that specify thatthe user device 100 should deny the request to perform the identifiedfunctions of the user device 100.

In some embodiments, event logs may be created that specify at least oneproperty describing the application of the identified watermark template156 to the function of the user device 100 and/or the authorization ofthe request to perform the function of the user device 100. Event logsmay, for example, specify at least one of a user identifier, a deviceidentifier, a determination of whether the user device 100 complies withat least one compliance rule 158, a source identifier, a timestamp, anda location describing the context of the watermark template 156application step and/or the identified request authorization step. Eventlogs may, for instance, facilitate the management of the respective userdevice 100 by providing data necessary for the operations of enterprisemobility management services and/or the like. Accordingly, in certainembodiments, event logs may be transmitted to a service communicativelycoupled to the user device 100, such as a resource server 210, watermarktemplate server 220, and/or compliance server 230.

FIG. 4 is a flow chart setting forth the general stages involved in amethod 400 consistent with embodiments of this disclosure for providingresource watermarking and management. Method 400 may be implementedusing element(s) of operating environment 200, such as user device 100,resource server 210, watermark template server 220, compliance server230, and network 240, as described above. Ways to implement the stagesof method 400 will be described in greater detail below.

Method 400 may begin at starting block 405 and proceed to stage 410where a request to establish an association between a watermark template156 and a function of at least one user device 100 is identified. Incertain embodiments, a request to establish an association between awatermark template 156 and a function of at least one user device 100may include a request to establish an association between a watermarktemplate 156 and at least one resource 154 accessible to the function ofthe at least one user device 100. In particular, resources 154accessible to functions of user devices 100 may include resources 154created by such functions, resources 154 modified by such functions,resources 154 stored by such functions, and/or resources 154 transmittedby such functions.

In some embodiments, the at least one user device 100 may identify therequest to establish the association between the watermark template 156and the function of the at least one user device 100. For instance, atleast one agent application 250 executed by a user device 100 maymonitor the operations of the user device 100 to identify requests toestablish an association between a watermark template 156 and a functionof the user device 100. As another example, the function of the userdevice 100 from which a request is initiated may be configured toidentify the request to establish an association between the watermarktemplate 156 and the function of the user device 100. In someembodiments, a server communicatively coupled to a user device 100 mayidentify a request to establish an association between a watermarktemplate 156 and a function of the user device 100. For example, anenterprise mobility management server, such as a resource server 210, awatermark template server 220, and/or a compliance server 230 mayinstruct the operating system of a user device 100 via an API that theoperating system of the user device 100 should monitor the operations ofthe user device 100 to identify a request to establish an associationbetween a watermark template 156 and a function of the user device 100.

From stage 410, method 400 may advance to stage 415 where adetermination of whether the request to establish the associationbetween the watermark template 156 and the function of the user device100 is authorized to be made. In certain embodiments, the determinationof whether a request to establish an association between a watermarktemplate 156 and a function of a user device 100 may be made based atleast in part on whether at least one compliance rule 158 is satisfied.More specifically, compliance rules 158 may specify that only certainusers that are operating certain user devices 100 at certain locationsduring certain times may establish associations between watermarktemplates 156 and functions of the user devices 100. For instance,compliance rules 158 may specify that only police officer-users that areoperating police department-owned user devices 100 that are beingoperated at locations of crime scenes during standard workday hours mayestablish associations between watermark templates 156 and functions ofthe user devices 100. Additionally, compliance rules 158 may specifythat only certain administrators that are utilizing certain serverscommunicatively coupled to the user devices 100 may establishassociations between watermark templates 158 and functions of the userdevices 100. For example, compliance rules 158 may specify that onlyenterprise-employed IT administrators that are managing enterprise-owneduser devices 100 via an enterprise mobility management server to whichthe enterprise-owned user devices 100 are enrolled, and therebycommunicatively coupled, may establish associations between watermarktemplates 158 and functions of the user devices 100.

In some embodiments, the determination of whether a compliance rule 158is satisfied may be made based at least in part on whether a user of therespective user device 100 satisfies the compliance rule 158. Forinstance, a user may satisfy a certain compliance rule 158 if the userhas provided authorized user credentials, is employed by a certainenterprise, and/or holds a sufficiently privileged employment positionwith a certain enterprise. In some embodiments, the determination ofwhether a compliance rule 158 is satisfied may be made based at least inpart on whether the user device 100 satisfies the compliance rule 158.For example, a user device 100 may satisfy a compliance rule 158 if adevice profile 152 of the user device 100 indicates that the state ofthe user device 100 satisfies certain security requirements specified bythe compliance rule 158, such as whether data encryption is enabled onthe user device 100.

Additionally, in some embodiments, the determination of whether acompliance rule 158 is satisfied may be made based at least in part onwhether an administrator of a respective user device 100 satisfies thecompliance rule 158. For instance, an administrator may satisfy acompliance rule 158 if the administrator has provided authorizedadministrator credentials, is employed by a certain enterprise 158,and/or holds a sufficiently privileged employment position with acertain enterprise 158. In some embodiments, the determination ofwhether a compliance rule 158 is satisfied may be made based at least inpart on whether a server communicatively coupled to the user device 100satisfies the compliance rule 158. For example, a server communicativelycoupled to the user device 100 may satisfy a compliance rule 158 if theserver is located behind a firewall, is providing an enterprise mobilitymanagement service, and if the user device 100 communicatively coupledto the server is enrolled in the executed enterprise mobility managementservice.

From stage 415, method 400 may advance to stage 420 where a request toestablish an association between a watermark template 156 and a functionof a user device 100 may be authorized. In certain embodiments, requeststo establish an association between a watermark template 156 and afunction of a user device 100 may be authorized in response to adetermination that the requests are authorized based at least in part onat least one compliance rule 158 being satisfied.

In some embodiments, requests to establish an association between awatermark template 156 and a function of a user device 100 may beauthorized by instructing the user device 100 that the request isauthorized and/or by instructing the user device 100 to create anassociation record describing the association between the watermarktemplate 156 and the function of the user device 100. In someembodiments, requests to establish an association between a watermarktemplate 156 and a function of a user device 100 may be authorized bypermitting the user device 100 to establish such association withoutinterference, such as by taking no action. As an example, an agentapplication 250 may transmit commands to the operating system 115 of theuser device 100 via an API that specify that the user device 100 shouldauthorize the request to establish an association between a watermarktemplate 156 and a function of a user device 100. Additionally, acompliance server 230 may transmit commands to the user device 100and/or to functions of the user device 100 associated with the requestthat specify that the request to establish an association between awatermark template 156 and a function of a user device 100 should beauthorized.

In certain embodiments, authorizing a request to establish anassociation between a watermark template 156 and a function of a userdevice 100 may include establishing the association between thewatermark template 156 and the function of the user device 100. In someembodiments, establishing the association between the watermark template156 and the function of the user device 100 may include creating anassociation record describing the association between the watermarktemplate 156 and the function of the user device 100 and storing theassociation record in a memory. For instance, an association record maybe stored in a memory of the user device 100 and/or may be stored in awatermark template store 222 of a watermark template server 220communicatively coupled to the user device 100 via a network 240.

In certain embodiments, authorizing a request to establish anassociation between a watermark template 156 and a function of a userdevice 100 may include identifying at least one watermark templateelement, compiling the watermark template 156 from the identifiedwatermark template elements, and establishing the association betweenthe watermark template 156 and the function of the user device 100. Insome embodiments, watermark template elements may be identified byrequesting input of the watermark template elements. For example, themethod may request input of watermark template elements, such asdescriptive data elements, naming convention elements, and/or storagestructure convention elements, from a user of a user device 100 and/oran administrator of the user device 100. In some embodiments, watermarktemplate elements may be identified by querying at least one memoryaccessible to the user device 100 to determine whether the memories holdwatermark template elements in storage. For instance, watermark templateelements stored on a memory of a user device 100 and/or a memory of aserver communicatively coupled to the user device 100, such as awatermark template server 220, may be identified. In any case, uponcompleting the authorization step of stage 420, the method 400 may endat stage 425.

The method may further include steps to apply a watermark template 156established as associated with a function of a user device 100 to thefunction of the user device 100. In certain embodiments, a watermarktemplate 156 may be applied to a function of a user device 100 and/orresources 154 accessible to a function of a user device 100 as describedwith respect to FIG. 3. For instance, the method may identify a requestto perform a function of at least one user device 100, may identify anappropriate watermark template 156, may apply the appropriate watermarktemplate 156 to the function of the user device 100, and may authorizethe request to perform the function of the user device 100, where theappropriate watermark template 156 is identified via an associationestablished between the watermark template 156 and the function of theuser device 100 as described herein.

The method may yet further include denying the request to establish anassociation between a watermark template 156 and a function of the userdevice 100 in response to a determination that at least one compliancerule 158 is not satisfied. In certain embodiments, the method mayinclude denying the request to establish an association between awatermark template 156 and a function of the user device 100 in responseto a determination that a configured threshold of compliance rules 158is not satisfied. For instance, the method may deny a request toestablish an association between a watermark template 156 and a functionof a user device 100 if a user of the user device 100 does not satisfyall compliance rules 158 specific to such user and if the user device100 itself does not satisfy 75% of all compliance rules 158 specific tothe user device 100.

The method may yet further include steps to facilitate the management ofa user device 100, including functions of the user device 100, resources154 accessible to functions of the user device 100, and watermarktemplates 156 accessible to the user device 100. In certain embodiments,the method may include a step that creates an event log that describesthe steps taken by the method. In particular, event logs may be createdthat detail an identification of a request to establish an associationbetween a watermark template 156 and a function of a user device 100, adetermination of whether the request to establish the associationbetween the watermark template 156 and the function of the user device100 is authorized, and/or an authorization of the request to establishthe association between the watermark template 156 and the function ofthe user device 100. Additionally, an event log may be created thatdescribes an identification of a request to perform a function of a userdevice 100, an application of the appropriate watermark template 156 tothe function of the user device 100, and/or an authorization of therequest to perform the function of the user device 100. In someembodiments, the method may include a step that transmits the event logto a memory for storage, such as a memory of a user device 100 and/or amemory of a server communicatively coupled to a user device 100.

An embodiment consistent with the disclosure may comprise a method forproviding functionality watermarking and management. The method maycomprise identifying a request to establish an association between awatermark template and a function of at least one user device,determining whether the request to establish the association between thewatermark template and the function of the at least one user device isauthorized, and authorizing the request to establish the associationbetween the watermark template and the function of the at least one userdevice in response to a determination that the request to establish theassociation between the watermark template and the function of the atleast one user device is authorized.

Another embodiment consistent with the disclosure may comprise anapparatus for providing functionality watermarking and management. Theapparatus may comprise at least one processor and at least one memoryhaving program code instructions embodied therein, the at least onememory and program code instructions being configured to, with the atleast one processor, direct the apparatus to at least identifying arequest to establish an association between a watermark template and afunction of at least one user device, determining whether the request toestablish the association between the watermark template and thefunction of the at least one user device is authorized, and authorizingthe request to establish the association between the watermark templateand the function of the at least one user device in response to adetermination that the request to establish the association between thewatermark template and the function of the at least one user device isauthorized.

Yet another embodiment consistent with the disclosure may comprise acomputer program product for providing functionality watermarking andmanagement. The computer program product comprising a non-transitorycomputer-readable storage medium having program code portions embodiedtherein, the program code portions being configured to, upon execution,direct an apparatus to at least identifying a request to establish anassociation between a watermark template and a function of at least oneuser device, determining whether the request to establish theassociation between the watermark template and the function of the atleast one user device is authorized, and authorizing the request toestablish the association between the watermark template and thefunction of the at least one user device in response to a determinationthat the request to establish the association between the watermarktemplate and the function of the at least one user device is authorized.

The embodiments and functionalities described herein may operate via amultitude of computing systems, including wired and wireless computingsystems, mobile computing systems (e.g., mobile telephones, tablet orslate type computers, laptop computers, etc.). In addition, theembodiments and functionalities described herein may operate overdistributed systems, where application functionality, memory, datastorage and retrieval and various processing functions may be operatedremotely from each other over a distributed computing network, such asthe Internet or an intranet. User interfaces and information of varioustypes may be displayed via on-board computing device displays or viaremote display units associated with one or more computing devices. Forexample user interfaces and information of various types may bedisplayed and interacted with on a wall surface onto which userinterfaces and information of various types are projected. Interactionwith the multitude of computing systems with which embodiments of thisdisclosure may be practiced include, keystroke entry, touch screenentry, voice or other audio entry, gesture entry where an associatedcomputing device is equipped with detection (e.g., camera) functionalityfor capturing and interpreting user gestures for controlling thefunctionality of the computing device, and the like. The Figures aboveand their associated descriptions provide a discussion of a variety ofoperating environments in which embodiments of this disclosure may bepracticed. However, the devices and systems illustrated and discussedwith respect to the Figures are for purposes of example and illustrationand are not limiting of a vast number of computing device configurationsthat may be utilized for practicing embodiments of this disclosure asdescribed herein.

The term computer readable media as used herein may include computerstorage media. Computer storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, program modules, or other data. Systemmemory, removable storage, and non-removable storage are all computerstorage media examples (i.e., memory storage.) Computer storage mediamay include, but is not limited to, RAM, ROM, electrically erasableread-only memory (EEPROM), flash memory or other memory technology,CD-ROM, digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store.

The term computer readable media as used herein may also includecommunication media. Communication media may be embodied by computerreadable instructions, data structures, program modules, non-transitorymedia, and/or other data in a modulated data signal, such as a carrierwave or other transport mechanism, and includes any information deliverymedia. The term “modulated data signal” may describe a signal that hasone or more characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, radiofrequency (RF), infrared, and other wireless media.

A number of applications and data files may be used to perform processesand/or methods as described above. The aforementioned processes areexamples, and a processing unit may perform other processes. Otherprogramming modules that may be used in accordance with embodiments ofthis disclosure may include electronic mail, calendar, and contactsapplications, data processing applications, word processingapplications, spreadsheet applications, database applications, slidepresentation applications, drawing or computer-aided applicationprograms, etc.

Generally, consistent with embodiments of this disclosure, programmodules may include routines, programs, components, data structures, andother types of structures that may perform particular tasks or that mayimplement particular abstract data types. Moreover, embodiments of thedisclosure may be practiced with other computer system configurations,including hand-held devices, multiprocessor systems,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers, and the like. Embodiments of thisdisclosure may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotememory storage devices.

Furthermore, embodiments of this disclosure may be practiced in anelectrical circuit comprising discrete electronic elements, packaged orintegrated electronic chips containing logic gates, a circuit utilizinga microprocessor, or on a single chip containing electronic elements ormicroprocessors. Embodiments of this disclosure may also be practicedusing other technologies capable of performing logical operations suchas, for example, AND, OR, and NOT, including but not limited tomechanical, optical, fluidic, and quantum technologies. In addition,embodiments of the disclosure may be practiced within a general purposecomputer or in any other circuits or systems.

Embodiments of this disclosure may, for example, be implemented as acomputer process and/or method, a computing system, an apparatus,device, or appliance, and/or as an article of manufacture, such as acomputer program product or computer readable media. The computerprogram product may be a computer storage media readable by a computersystem and encoding a computer program of instructions for executing acomputer process. The computer program product may also be a propagatedsignal on a carrier readable by a computing system and encoding acomputer program of instructions for executing a computer process.Accordingly, the present disclosure may be embodied in hardware and/orin software (including firmware, resident software, micro-code, etc.).In other words, embodiments of the present disclosure may take the formof a computer program product on a computer-usable or computer-readablestorage medium having computer-usable or computer-readable program codeembodied in the medium for use by or in connection with an instructionexecution system. A computer-usable or computer-readable medium may beany medium that can contain, store, communicate, propagate, or transportthe program for use by or in connection with the instruction executionsystem, apparatus, or device.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. More specific computer-readable medium examples (anon-exhaustive list), the computer-readable medium may include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, and a portable compact disc read-only memory(CD-ROM). Note that the computer-usable or computer-readable mediumcould even be paper or another suitable medium upon which the program isprinted, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, or otherwise processed in a suitable manner, if necessary,and then stored in a computer memory.

Embodiments of this disclosure may be practiced via a system-on-a-chip(SOC) where each and/or many of the elements described above may beintegrated onto a single integrated circuit. Such an SOC device mayinclude one or more processing units, graphics units, communicationsunits, system virtualization units and various applicationfunctionalities, all of which may be integrated (or “burned”) onto thechip substrate as a single integrated circuit. When operating via anSOC, the functionality, described herein, with respect to trainingand/or interacting with any element may operate via application-specificlogic integrated with other components of the computing device/system onthe single integrated circuit (chip).

Embodiments of this disclosure are described above with reference toblock diagrams and/or operational illustrations of methods, systems, andcomputer program products according to embodiments of the disclosure.The functions/acts noted in the blocks may occur out of the order asshown in any flowchart. For example, two blocks shown in succession mayin fact be executed substantially concurrently or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality/acts involved.

While certain embodiments have been described, other embodiments mayexist. Furthermore, although embodiments of the present disclosure havebeen described as being associated with data stored in memory and otherstorage mediums, data can also be stored on or read from other types ofcomputer-readable media, such as secondary storage devices, like harddisks, floppy disks, or a CD-ROM, a carrier wave from the Internet, orother forms of RAM or ROM. Further, the disclosed methods' stages may bemodified in any manner, including by reordering stages and/or insertingor deleting stages, without departing from the disclosure.

Embodiments of the present disclosure, for example, are described abovewith reference to block diagrams and/or operational illustrations ofmethods, systems, and computer program products according to embodimentsof the disclosure. The functions/acts noted in the blocks may occur outof the order as shown in any flowchart. For example, two blocks shown insuccession may in fact be executed substantially concurrently or theblocks may sometimes be executed in the reverse order, depending uponthe functionality/acts involved.

While certain embodiments of the disclosure have been described, otherembodiments may exist. Furthermore, although embodiments of the presentdisclosure have been described as being associated with data stored inmemory and other storage mediums, data can also be stored on or readfrom other types of computer-readable media, such as secondary storagedevices, like hard disks, floppy disks, or a CD-ROM, a carrier wave fromthe Internet, or other forms of RAM or ROM. Further, the disclosedmethods' stages may be modified in any manner, including by reorderingstages and/or inserting or deleting stages, without departing from thedisclosure.

All rights including copyrights in the code included herein are vestedin and the property of the Assignee. The Assignee retains and reservesall rights in the code included herein, and grants permission toreproduce the material only in connection with reproduction of thegranted patent and for no other purpose.

While the specification includes examples, the disclosure's scope isindicated by the following claims. Furthermore, while the specificationhas been described in language specific to structural features and/ormethodological acts, the claims are not limited to the features or actsdescribed above. Rather, the specific features and acts described aboveare disclosed as example for embodiments of the disclosure.

What is claimed is:
 1. A non-transitory computer-readable mediumembodying program code executable in at least one computing device that,when executed, causes the at least one computing device to: identify arequest to establish an association between a watermark template and afunction capable of being performed on a client device, the requestbeing performed by an administrator through a console application,wherein, if associated, the watermark template is applied to the atleast one resource in response to the function being performed on theclient device; determine whether the request to establish theassociation between the watermark template and the function of theclient device is authorized based at least in part on a role of theadministrator complying with at least one compliance rule, the at leastone compliance rule specifying that the administrator has authorizationto manage the client device through a mobility management service; andresponsive to a determination that the request to establish theassociation between the watermark template with the function of theclient device is authorized, cause an agent application executable onthe client device to establish the association between the watermarktemplate and the function of the client device where the watermarktemplate is applied to the at least one resource in response to thefunction being subsequently performed on the client device, whereinapplying the watermark template to the at least one resource comprisescausing at least a portion of the watermark template to be overlaid ontoat least one graphical user interface (GUI) associated with the clientdevice.
 2. The non-transitory computer-readable medium of claim 1,further comprising program code that, when executed, causes the clientdevice to authorize the request to establish the association between thewatermark template and the function of client device by: identifying atleast one watermark template element; compiling the watermark templatefrom the at least one watermark template element as identified; andestablishing the association between the watermark template and thefunction of the client device.
 3. The non-transitory computer-readablemedium of claim 2, wherein the at least one watermark template elementfurther comprises at least one descriptive data element, at least onenaming convention element, or at least one storage structure conventionelement.
 4. The non-transitory computer-readable medium of claim 2,further comprising program code that, when executed, causes the clientdevice to identify the at least one watermark template element frommemory.
 5. The non-transitory computer-readable medium of claim 4,wherein the program code that, when executed, causes the client deviceto identify the at least one watermark template element from the memoryfurther comprises program code that, when executed, causes the clientdevice to request an input of the at least one watermark templateelement.
 6. The non-transitory computer-readable medium of claim 5,wherein the program code that, when executed, causes the client deviceto request the input of the at least one watermark template elementfurther comprises program code that, when executed, causes the clientdevice to request the input of the at least one watermark templateelement from a user of the client device or the administrator.
 7. Thenon-transitory computer-readable medium of claim 2, wherein the role ofthe administrator comprises an information technology (IT) administratorrole.
 8. A system, comprising: a user device comprising a local datastore; and program instructions executable in the user device that, whenexecuted by at least one hardware processor of the user device, causethe user device to: identify a request to establish an associationbetween a watermark template and a function capable of performance onthe user device, the request being performed by an administrator,wherein, if associated, the watermark template is applied to the atleast one resource in response to the function being performed on theclient device; determine whether the request to establish theassociation between the watermark template and the function of the userdevice is authorized based at least in part on a role of theadministrator complying with at least one compliance rule, the at leastone compliance rule specifying that the administrator has authorizationto manage the client device through a mobility management service; andresponsive to a determination that the request to establish theassociation between the watermark template with the function of the userdevice is authorized, cause an agent application executable on theclient device to establish the association between the watermarktemplate and the function of the user device such that the watermarktemplate is applied to the at least one resource in response to thefunction subsequently being performed on the client device, whereinapplying the watermark template to the at least one resource comprisescausing at least a portion of the watermark template to be overlaid ontoat least one graphical user interface (GUI) associated with the clientdevice.
 9. The system of claim 8, further comprising programinstructions that, when executed, cause the user device to authorize therequest to establish the association between the watermark template andthe function of user device by: identifying at least one watermarktemplate element; compiling the watermark template from the at least onewatermark template element as identified; and establishing theassociation between the watermark template and the function of the userdevice.
 10. The system of claim 9, wherein the at least one watermarktemplate element further comprises at least one descriptive dataelement, at least one naming convention element, or at least one storagestructure convention element.
 11. The system of claim 9, wherein theprogram instructions that, when executed, cause the user device toidentify the at least one watermark template element further compriseprogram instructions that, when executed, cause the user device torequest an input of the at least one watermark template element.
 12. Thesystem of claim 11, wherein the program instructions that, whenexecuted, cause the user device to request the input of the at least onewatermark template element further comprise program instructions that,when executed, cause the user device to request the input of the atleast one watermark template element from a user of the user device orthe administrator.
 13. The system of claim 9, wherein the programinstructions that, when executed, cause the user device to identify theat least one watermark template element further comprise programinstructions that, when executed, cause the user device to identify atleast one watermark template element from the local data store or aremote data store.
 14. The system of claim 8, wherein the role of theadministrator comprises an information technology (IT) administratorrole.
 15. A method, comprising: identifying, by a computing devicecomprising at least one hardware processor, a request to establish anassociation between a watermark template and a function capable of beingperformed on a client device, the request being performed by anadministrator through a console application, wherein, if associated, thewatermark template is applied to the at least one resource in responseto the function being performed on the client device; determining, bythe computing device, whether the request to establish the associationbetween the watermark template and the function of the client device isauthorized based at least in part on a role of the administratorcomplying with at least one compliance rule, the at least one compliancerule specifying that the administrator has authorization to manage theclient device through a management service; and responsive to adetermination that the request to establish the association between thewatermark template with the function of the client device is authorized,causing, by the computing device, an application executable on theclient device to establish the association between the watermarktemplate and the function of the client device where the watermarktemplate is applied to the at least one resource in response to thefunction being subsequently performed on the client device, whereinapplying the watermark template to the at least one resource comprisescausing at least a portion of the watermark template to be overlaid ontoat least one graphical user interface (GUI) associated with the clientdevice.
 16. The method of claim 15, further comprising authorizing, bythe computing device, the request to establish the association betweenthe watermark template and the function of client device by:identifying, by the computing device, at least one watermark templateelement; compiling, by the computing device, the watermark template fromthe at least one watermark template element as identified; andestablishing, by the computing device, the association between thewatermark template and the function of the client device.
 17. The methodof claim 16, wherein the at least one watermark template element furthercomprises at least one descriptive data element, at least one namingconvention element, or at least one storage structure conventionelement.
 18. The method of claim 16, wherein identifying, by thecomputing device, the at least one watermark template element furthercomprises requesting, by the computing device, an input of the at leastone watermark template element.
 19. The method of claim 18, whereinrequesting, by the computing device, the input of the at least onewatermark template element further comprises requesting, by thecomputing device, the input of the at least one watermark templateelement from a user of the client device or an administrator of theclient device.
 20. The method of claim 18, wherein the role of theadministrator comprises an information technology (IT) administratorrole.